-
Notifications
You must be signed in to change notification settings - Fork 708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add create shcmea for sqlalchemy datastore #965
Conversation
You checked the boxes for having updated the documentation and added a changelog. Can you point out to me where you've done this? |
Please don't add unrelated changes to this PR. |
7997045
to
7eac782
Compare
I will make the necessary updates in |
d326891
to
3060ce9
Compare
I've updated |
Please merge from master because your force pushes are now undoing the updates I made. |
697b3c1
to
975a7d5
Compare
Could you please stop force-pushing your changes? It's causing some previous updates from |
Thanks! |
Changes
Add create shcmea for sqlalchemy datastore
Fixes #.
Checklist
If this is a user-facing code change, like a bugfix or a new feature, please ensure that
you've fulfilled the following conditions (where applicable):
tests/
) added which would fail without your patchdocs/
, in case of behavior changes or newfeatures)
docs/versionhistory.rst
).If this is a trivial change, like a typo fix or a code reformatting, then you can ignore
these instructions.
Updating the changelog
If there are no entries after the last release, use
**UNRELEASED**
as the version.If, say, your patch fixes issue #999, the entry should look like this:
* Fix big bad boo-boo in the async scheduler (#999 <https://github.com/agronholm/apscheduler/issues/999>_; PR by @yourgithubaccount)
If there's no issue linked, just link to your pull request instead by updating the
changelog after you've created the PR.